Oracle VM (OVM) (MOSC)

MOSC Banner

Migration of domU broken in 3.3.2?

edited Apr 5, 2015 6:22AM in Oracle VM (OVM) (MOSC) 7 commentsAnswered ✓

Hi,

I've upgraded my demo/poc environment to 3.3.2 and notice strange issue on the source server (the one migration is taken from):

[root@ovs1 log]# xm list

Name                                        ID   Mem VCPUs      State   Time(s)

0004fb0000060000300e0bb57dc4c4d8             2 16387     2     -b----    166.1

0004fb0000060000ec14a6c54180220c             3  8192     2     -b----    406.2

0004fb0000060000f5a09939d35ed32f             5 10240     2     r-----    882.1

Domain-0                                     0  2103    12     r-----   1192.2

Domain-Unnamed                               1  8192     2     --ps--   1057.1

There is remain of migrated domain called "Domain-Unnamed". Subsequent migrations create more such domains and they do seem to hold memory.

Downgrading xen and xen-tools packages seem to resolve this.

Has anyone notice the same? How to solve this?

Regards,

Michal

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center