RE: [Xen-users] Trouble trying to use vmware within XEN Dom0

["Petersson, Mats" <Mats.Petersson@xxxxxxx>]

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Ulrich Windl
> Sent: 06 October 2006 14:10
> To: Janke Dávid
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Trouble trying to use vmware within XEN Dom0
> 
> On 6 Oct 2006 at 13:37, Janke Dávid wrote:
> 
> > Hi Ulrich!
> > 
> > If you parse the list archive, we discussed this. 
> Unfortunately it won't
> > work. Use a VT enabled system and HVM for Windows installs. 
> Or a seperate
> > server.
> 
> OK, I agree it wouldn't work, so I guess XEN would also fail 
> under VMware, right?
> I was only reporting this because there was a kernel problem, 
> and I was not sure 
> whether the vmware modules have the problem, or the XEN code, 
> or the stck 
> kernel...

Yes, Xen will not work on top of VMWare, for exactly the same reason - again, 
it's theoretically possible to make it work - but I would expect that it's not 
on the top of VMWares or Xen's list of things to do... ;-)

--
Mats
> 
> Regards,
> Ulrich
> 
> > 
> > David
> > 
> > On 10/6/06, Ulrich Windl <ulrich.windl@xxxxxxxxxxxxxxxxxxxx> wrote:
> > >
> > > Hi,
> > >
> > > it seems using vmware within XEN is the ultimate test for XEN.
> > > Unfortunately it
> > > does not work (SLES10 on x86_64 (latest) with VMware 
> Server 1.0.1):
> > >
> > > The Linux gets an Oops or panic:
> > > Oct  6 11:05:34 rkdvmso1 kernel: CPU 2
> > > Oct  6 11:05:34 rkdvmso1 kernel: Modules linked in: vmnet 
> parport_pc
> > > parport vmm
> > > on xt_physdev xt_pkttype ipt_LOG xt_limit bridge blkbk 
> netbk netloop nfsd
> > > eeprom
> > > exportfs lockd lm92 nfs_acl adm1026 hwmon_vid hwmon 
> sunrpc i2c_isa sr_mod
> > > af_pa
> > > cket button battery ac ip6t_REJECT xt_tcpudp ipt_REJECT xt_state
> > > iptable_mangle
> > > iptable_nat ip_nat iptable_filter ip6table_mangle 
> ip_conntrack nfnetlink
> > > ip_tabl
> > > es ip6table_filter ip6_tables x_tables ipv6 loop 
> usb_storage usbhid dm_mod
> > > hw_ra
> > > ndom i2c_amd8111 i2c_amd756 i2c_core ide_cd ohci_hcd 
> usbcore e1000 cdrom
> > > shpchp
> > > pci_hotplug reiserfs fan thermal processor sg mptsas 
> mptscsih mptbase
> > > scsi_trans
> > > port_sas amd74xx sd_mod scsi_mod ide_disk ide_core
> > > Oct  6 11:05:34 rkdvmso1 kernel: Pid: 7300, comm: 
> vmware-vmx Tainted:
> > > P     U 2.
> > > 6.16.21-0.25-xen #1
> > > Oct  6 11:05:34 rkdvmso1 kernel: RIP: e030:[<ffffffff883483a2>]
> > > <ffffffff883483a
> > > 2>{:vmmon:Task_Switch+503}
> > > [...]
> > > Oct  6 11:05:34 rkdvmso1 kernel: Process vmware-vmx (pid: 
> 7300, threadinfo
> > > ffff8
> > > 803bccba000, task ffff8803ea591880)
> > > [...]
> > > Oct  6 11:05:34 rkdvmso1 kernel: Call Trace:
> > > <ffffffff8834ac5e>{:vmmon:Vmx86_RunVM+63}
> > > Oct  6 11:05:34 rkdvmso1 kernel:
> > > <ffffffff88343a8e>{:vmmon:LinuxDriver_Ioctl+317}
> > > <ffffffff8010d7e7>{monotonic_clock+53}
> > > Oct  6 11:05:34 rkdvmso1
> > > kernel:        <ffffffff802c5fe9>{thread_return+0}
> > > <ffffffff8012e937>{do_setitimer+936}
> > > Oct  6 11:05:34 rkdvmso1 kernel:
> > > <ffffffff8834423e>{:vmmon:LinuxDriver_CompatIoctl+35}
> > > Oct  6 11:05:34 rkdvmso1
> > > kernel:        <ffffffff801980ac>{compat_sys_ioctl+206}
> > > <ffffffff80119ca5>{ia32_sysret+0}
> > > [...]
> > >
> > > Regards,
> > > Ulrich
> > >
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-users
> > >
> > 
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 
> 



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users