I am running xen-unstable (change log 23842) and linux 3.0 (ubuntu 10.10) on a Lenovo x220. I am having trouble installing ubuntu 11.04 64-bit with the following config file: builder=''hvm'' memory = 1024 name = ''ubuntu'' vcpus = 2 pae = 1 acpi = 1 apic = 1 vif = [ '''' ] disk = [''/dev/vg/ubuntu,raw,hda,w'',''/var/xen/isos/ubuntu-11.04-server-amd64.iso,raw,hdc,devtype=cdrom,r''] vnc = 0 sdl = 1 Both the disk and network devices are not recognized by the installer. The disk is of course the killer. I get a message saying "No disk driver was detected" and a list of drivers to choose from. None of the drivers work. Is something wrong with my configuration file? I have also included the qemu log file output BTW, I was able to install CentOS 5.6 and Windows 7 without any issues. Thanks, AP LOG OUTPUT --------------------- videoram option does not work with cirrus vga device model. Videoram set to 4M. Using file /dev/vg/ubuntu in read-write mode Strip off blktap sub-type prefix to /var/xen/isos/ubuntu-11.04-server-amd64.iso (drv ''aio'') Using file /var/xen/isos/ubuntu-11.04-server-amd64.iso in read-only mode Watching /local/domain/0/device-model/20/logdirty/cmd Watching /local/domain/0/device-model/20/command Watching /local/domain/20/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 53650e46-1301-4a00-964b-ad0852ad2026 populating video RAM at ff000000 mapping video RAM from ff000000 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/20/xen_extended_power_mgmt): read error medium change watch on `hdc'' (index: 1): aio:/var/xen/isos/ubuntu-11.04-server-amd64.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. xs_read(/local/domain/20/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/20/log-throttling'' medium change watch on `/local/domain/20/log-throttling'' - unknown device, ignored cirrus vga map change while on lfb mode mapping vram to f0000000 - f0400000 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. Unknown PV product 3 loaded in guest PV driver build 1 region type 1 at [c100,c200). region type 0 at [f3001000,f3001100). squash iomem [f3001000, f3001100). _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Why ubuntu as hvm domu and not pv? I have installed Natty as pv, with official netinstall take here: http://archive.ubuntu.com/ubuntu/dists/natty/main/installer-amd64/current/images/netboot/xen/ Have 2 problem on install solved: On network interfaces detection failed select "go back" select execute shell, insert this command: modprobe xen-netfront exit select "Detect network hardware" continue with normal install and at bootloader problem select to continue without bootloader. At install complete mount domu disk with -o loop on dom0 and create file for pygrub, for example: mkdir /mnt/tmp/boot/grub vi /mnt/tmp/boot/grub/menu.lst #check always kernel version ---------------------------------------------------------- default 0 timeout 2 title Natty 64 bit (Ubuntu 11.04) root (hd0,0) kernel /boot/vmlinuz-2.6.38-11-generic root=/dev/xvda1 ro initrd /boot/initrd.img-2.6.38-11-generic title Natty 64 bit (Ubuntu 11.04) (Single-User) root (hd0,0) kernel /boot/vmlinuz-2.6.38-11-generic root=/dev/xvda1 ro single initrd /boot/initrd.img-2.6.38-11-generic ---------------------------------------------------------- Start the first time and solve the other problem, for example: xm create NATTY.cfg xm console NATTY.cfg modprobe xen-blkfront exit # login and add xen modules # Add in /etc/initramfs-tools/modules and /etc/modules: ---------------------------------------------------------- xen_netfront #Xen virtual network device frontend xen_blkfront #Xen virtual block device frontend xen_fbfront #Xen virtual framebuffer device frontend xen_kbdfront #Xen virtual keyboard/pointer device frontend ---------------------------------------------------------- sudo update-initramfs -u sudo reboot You can also install grub2 without problem on domu active now: sudo rm /boot/grub/menu.lst sudo aptitude install grub sudo update-grub I have all working except 2 problem: - Xen vnc pointer doesn''t work after restore - Cdrom in cfg file, see example below: disk=[''tap2:aio:/mnt/vm/disks/NATTY.disk1.xm,xvda1,w'', ''tap2:aio:/mnt/vm/disks/NATTY.disk2.xm,xvda2,w'', ''phy:/dev/scd0,xvdb:cdrom,r''] is seen as internal disk and only administrator can mount it -- View this message in context: http://xen.1045712.n5.nabble.com/Ubuntu-11-04-64-bit-HVM-on-xen-unstable-23842-tp4812413p4825514.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
AP
2011-Sep-23 05:22 UTC
Re: [Xen-users] Re: Ubuntu 11.04 64-bit HVM on xen-unstable 23842
On Sep 21, 2011 1:08 AM, "Fantu" <fantonifabio@tiscali.it> wrote:> > Why ubuntu as hvm domu and not pv?I am trying out nested virtualization which is why I need it to be a HVM domain.> I have installed Natty as pv, with official netinstall take here: >http://archive.ubuntu.com/ubuntu/dists/natty/main/installer-amd64/current/images/netboot/xen/> Have 2 problem on install solved: > On network interfaces detection failed select "go back" select execute > shell, insert this command: > modprobe xen-netfront > exit > select "Detect network hardware" > continue with normal install and at bootloader problem select to continue > without bootloader. > At install complete mount domu disk with -o loop on dom0 and create filefor> pygrub, for example: > mkdir /mnt/tmp/boot/grub > vi /mnt/tmp/boot/grub/menu.lst #check always kernel version > ---------------------------------------------------------- > default 0 > timeout 2 > > title Natty 64 bit (Ubuntu 11.04) > root (hd0,0) > kernel /boot/vmlinuz-2.6.38-11-generic root=/dev/xvda1 ro > initrd /boot/initrd.img-2.6.38-11-generic > > title Natty 64 bit (Ubuntu 11.04) (Single-User) > root (hd0,0) > kernel /boot/vmlinuz-2.6.38-11-generic root=/dev/xvda1 ro single > initrd /boot/initrd.img-2.6.38-11-generic > ---------------------------------------------------------- > Start the first time and solve the other problem, for example: > xm create NATTY.cfg > xm console NATTY.cfg > modprobe xen-blkfront > exit > # login and add xen modules > # Add in /etc/initramfs-tools/modules and /etc/modules: > ---------------------------------------------------------- > xen_netfront #Xen virtual network device frontend > xen_blkfront #Xen virtual block device frontend > xen_fbfront #Xen virtual framebuffer device frontend > xen_kbdfront #Xen virtual keyboard/pointer device frontend > ----------------------------------------------------------Yes this will solve the issue if you are running a PV domain. I think something similar is happening with the HVM domain. My guess is that the 11.04 kernel does not have the drivers for the disk adapter being exposed by QEMU.> sudo update-initramfs -u > sudo reboot > > You can also install grub2 without problem on domu active now: > sudo rm /boot/grub/menu.lst > sudo aptitude install grub > sudo update-grub > > I have all working except 2 problem: > > - Xen vnc pointer doesn''t work after restore > > - Cdrom in cfg file, see example below: > disk=[''tap2:aio:/mnt/vm/disks/NATTY.disk1.xm,xvda1,w'', > ''tap2:aio:/mnt/vm/disks/NATTY.disk2.xm,xvda2,w'', > ''phy:/dev/scd0,xvdb:cdrom,r''] > > is seen as internal disk and only administrator can mount it > > > -- > View this message in context:http://xen.1045712.n5.nabble.com/Ubuntu-11-04-64-bit-HVM-on-xen-unstable-23842-tp4812413p4825514.html> Sent from the Xen - User mailing list archive at Nabble.com. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Maybe Matching Threads
- Bug report about Windows 7 pro 64 bit domU on xen-unstable dom0 with qemu traditional
- Re: Xen-users Digest, Vol 64, Issue 52
- tap2:remus:backup_ip:9000|aio:/path_to_disk.img not working - OSError: [Errno 2] No such file or directory
- Kernel DomU 2.6.36.1 dont boot PVonHVM
- Kernel DomU 2.6.36.1 dont boot PVonHVM